Release 10.1A: OpenEdge Development:
Progress Dynamics Administration

<services> node

The <services> node of the icfconfig.xml file contains a subordinate <service> node for each of the services that must be connected for the session to work. Note that only services that are required to gain access to the Repository must be specified. Once the session has made its connection to the Repository through the Connection Manager, all further information can be derived from the Repository instead of from the icfconfig.xml file.

Prior to making the connections to the services, the Configuration File Manager starts the Connection and Service Type managers that are required to make all of the connections. To begin the services connection process, the Configuration File Manager populates a services temp-table (ttService) with data contained in the services node. The entire services temp-table is passed to the Connection Manager so that it can establish the appropriate connections. For more information on how the Connection Manager establishes connections, see OpenEdge Development: Progress Dynamics Managers API Reference .

Each service node contains the following nodes of its own:

<cServiceType> — This field contains the type of service that is to be connected, defined inside the Repository. For each cServiceType, there must be an ICFCM_ property that points to the appropriate manager name. This field maps to gsc_service_type.service_type_code.
<cServiceName> — This field contains the logical name of the service to be connected. This field maps to gsc_logical_service.logical_service_code.
<cPhysicalService> — This field contains the physical name of the service that is being used from the Repository. This field maps to gsm_physical_service.physical_service_code.
<cConnectParams> — This field contains the connection parameters of the service that is being used. This field maps to gsm_physical_service.connection_parameters.
<lDefaultService> — This field contains a logical variable indicating whether or not this is the default service for this service type. This field is derived from gsc_service_type.default_logical_service_obj.
<lCanRunLocal> — This field contains a logical variable indicating whether or not this service can be connected to the local session. This field maps to gsc_logical_service.can_run_locally.